Who does what, and how they connect. Three roles, six components, one
operating rhythm — the part of the framework that actually runs.
Components6
StructureThree Roles
OwnershipAI Transformation Lead
CadenceWeekly
Foxpath™
Operating Model · Three Roles · Six ComponentsHow the framework actually runs
Six components, what each one does
Reading order: structure first
Component 01Architecture
Three-Role Structure
What:AI Transformation Lead (central strategy + build), AI Champions (embedded BU execution), Executive Sponsor (active governance + escalation). The three roles work as one team with distinct mandates.
Why: Without role clarity, the framework becomes a side project. With it, every decision has a known owner.
LeadSponsorChampions
Component 02Core Role
Executive Sponsor
What: Chairs quarterly program review. Makes binding escalation decisions within 5 business days. Provides active air cover for Champions across the organization.
Why: Champions are only as protected as their exec air cover. Without binding authority above them, the role collapses at the first real conflict.
5-Day SLAQuarterly ReviewActive Cover
Component 03Recruitment
Champion Selection
What: High performers identified and recruited centrally. Selected for influence, credibility, and functional knowledge, not just enthusiasm. Each business unit gets a dedicated Champion.
Why: The wrong Champions will burn through the framework's credibility in a quarter. The right ones become force multipliers.
Influence FirstCredibilityBU Coverage
Component 04Responsibilities
Champion Mandate
What: Run monthly discovery sessions, own BU pipeline entries, represent the AI program inside the business unit, and report blockers weekly. Mandate is documented and tied to performance review.
Why: Vague mandates produce vague contribution. Concrete responsibilities are how Champions stay accountable and visible.
Monthly DiscoveryOwn PipelineWeekly Blockers
Component 05Discovery
Use Case Discovery Tool
What: Turns workflow conversations into scored, risk-tiered AI opportunities. Built first, used in every Champion discovery session. Outputs land directly in the Pipeline Tracker.
Why: Discovery sessions without a tool produce notes. Discovery sessions with a tool produce queue-ready use cases — the operating model's intake mechanism, in Champion hands.
Structured CaptureAuto-ScoreTracker Sync
Component 06Operating Rhythm
Weekly Cadence
What: Weekly Champion sync for pipeline updates and blocker removal. Dedicated channel for real-time coordination between syncs. Monthly all-hands rolls up to the quarterly Executive review.
Why: An operating model without a heartbeat decays into individual heroics. The cadence is how the model breathes.
Weekly SyncAsync ChannelQuarterly Roll-Up
Operating Model ownership
Who runs what
AI Transformation Lead
Owns the program. Runs central strategy, build, and methodology.
AI Champions
Embedded in each BU. Drive discovery, pipeline, and adoption.
Executive Sponsor
Authority + air cover. Owns binding escalation within 5 days.
"You can't delegate adoption without delegating authority. The operating model is where that line gets drawn."